﻿<!DOCTYPE html>
<html>
<head>
   <title>Signals Setup</title>
   <meta name="generator" content="Help & Manual">
   <meta name="keywords" content="">
   <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   <link type="text/css" href="default.css" rel="stylesheet">
   <link type="text/css" href="custom.css" rel="stylesheet">
   <script type="text/javascript" src="nsh.js"></script>
   
<!-- non-scrolling headers for CHM and browser-based help, local styles-->
<style TYPE="text/css" media="screen"> 
   <!-- 
   body {    
      margin:0; 
      padding:0; 
      overflow: auto; 
      background: #edede9; 
   } 
   #idheader { 
      width:100%; 
      height:auto; 
      padding: 0; 
      margin: 0;     
} 
    #idheaderbg  {
    background: #E40A00; 
}
#idheadernowrap  {
    white-space:nowrap; 
}
    ul {list-style-type: lower-roman}
   -->
   </style>
   
<style TYPE="text/css" MEDIA="print">
<!--
/* Hide navigation links and add space between header
     and text in the printed version. Not valid for eBooks. */
#idnav { display:none;	 }
.topichead { padding: 5px 5px 20px 5px; }
-->
</style>   
   <script type="text/javascript" src="jquery.js"></script>
   <script type="text/javascript" src="helpman_settings.js"></script>
   <script type="text/javascript" src="helpman_topicinit.js"></script>

   <script type="text/javascript">
     HMSyncTOC("index.html", "drvsim_confsignals_setup.htm");
   </script>
   <script type="text/javascript" src="highlight.js"></script>
   <script type="text/javascript">
     $(document).ready(function(){highlight();});
   </script>
</head>
<body>

<!--ZOOMSTOP-->

<div id="idheader" >
<div id="idheaderbg">
<table width="100%" border="0" cellspacing="0" cellpadding="0" 
       style="margin: 0px; color: #D7D7D7;">

  <tr valign="middle">
    <td align="left" valign="middle" class="topichead">
    <!--<div id="idheadernowrap">-->
    <p class="crumbs" id="idnav"><b>Navigation:</b>&nbsp;
   
   VI-DriveSim 19.2 on Linux &gt; VI-DriveSim 19.2 Configuration &gt; <a href="drivesim_drivesim_interface.htm">VI-DriveSim Interface</a> &gt; <a href="drivesim_gui_tab_config.htm">Configuration</a>&nbsp;&gt;</p>
      <h1 class="p_Heading1" style="page-break-after: avoid;"><span class="f_Heading1">Signals Setup</span></h1>

    <!--</div>-->
    </td>
    <td align="right" width="180" valign="middle" class="topichead" id="idnav">
    <div id="idheadernowrap">
    <a href="javascript: print();"
    		onmouseover="document.images.prntr.src='print_a.png'" 
        onmouseout="document.images.prntr.src='print_n.png'"
        ><img name="prntr" border="0" alt="Print this Topic" title="Print this Topic" src="print_n.png"
        ></a>&nbsp;&nbsp;
     <a href="drvsim_confprod_name_run_configuration.htm"
        onmouseover="document.images.prev.src='back_a.png'" 
        onmouseout="document.images.prev.src='back_n.png'"
        ><img name=prev src="back_n.png" border=0 alt="Previous page"
        ></a><a href="drivesim_gui_tab_config.htm"
        onmouseover="document.images.main.src='top_a.png'" 
        onmouseout="document.images.main.src='top_n.png'"><img name=main src="top_n.png" border=0 alt="Return to chapter overview"
        ></a><a href="drvsim_confmonitor.htm"
        onmouseover="document.images.next.src='next_a.png'" 
        onmouseout="document.images.next.src='next_n.png'"><img name=next src="next_n.png" border=0 alt="Next page"
        ></a>
    </div>
    </td>
  </tr>
</table>
</div>

<!-- The following code displays Expand All/Collapse All links  below the header in topics containing toggles -->
  

</div>  



<div id="idcontent"><div id="innerdiv"> 
<!--ZOOMRESTART-->
<p class="p_Normal">At the top right of the window there are all the buttons that let you manage the signals and their initial values, on the <span style="font-weight: bold;">Signals Setup</span> group. A brief description of the buttons and their actions is presented below:</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal"><span style="font-weight: bold;">CSV save: </span>this button will open the following window to select/deselect channels to log in a .csv file, the same set of signal could also be streamed to 3rd party telemetry tools.</p>
<p class="p_Normal" style="text-align: center;">&nbsp;</p>
<p class="p_Normal" style="text-align: center;"><img alt="drvsim_interface_csv_save" width="634" height="413" style="margin:0px auto 0px auto;width:634px;height:413px;border:none" src="drvsim_interface_csv_save.png"/></p>
<p class="p_Normal" style="text-align: center;">&nbsp;</p>
<p class="p_Normal"><a id="vicrt_inputs_config" class="hmanchor"></a><span style="font-weight: bold;">VI-CRT Inputs: </span>this button will open the following window to connect/disconnect channels from VI-DriveSim to VI-CarRealTime, for example in the following image user inputs are connected (green color) so they are transferred at each simulation step to VI-CarRealTime.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal" style="text-align: center;"><img alt="drvsim_interface_vicrt_inputs" width="634" height="390" style="margin:0px auto 0px auto;width:634px;height:390px;border:none" src="drvsim_interface_vicrt_inputs.png"/></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">A particular attention must be paid to the <span style="font-style: italic;">Driver_Demands</span> inputs, because they contain two categories of driver inputs, as reported in the following figure:</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal" style="text-align: center;"><img alt="drvsim_interface_vicrt_inputs_driverdemands" width="287" height="312" style="margin:0px auto 0px auto;width:287px;height:312px;border:none" src="drvsim_interface_vicrt_inputs_driverdemands.png"/></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">These categories are:</p>
<p style="text-align: justify; text-indent: 0px; padding: 0px 0px 0px 13px; margin: 0px 0px 0px 0px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span><span style="font-style: italic;">user_input_braking, user_input_clutch, user_input_gear, user_input_steering, user_input_throttle</span>: these inputs are VI-CarRealTime USER. The USER signal is a method to connect an external routine producing generic signals to the desired control channel and they represent the input signals from the driving simulator. &nbsp;</p><p class="p_Normal">&nbsp;</p>
<p class="p_Normal">These channels are specified in the <span style="font-weight: bold;">user_event.vdf</span> file and this is the file used as default in the VI-DriveSim event specification of the VI-CarRealTime model.</p>
<p style="text-align: justify; text-indent: 0px; padding: 0px 0px 0px 13px; margin: 0px 0px 0px 0px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span><span style="font-style: italic;">brake, clutch, gear, str_swa, throttle</span>: these inputs correspond to the signals that are added to the control channels of the VI-CarRealTime's internal driver. These control channels are set to 0 in the .vdf file so the signals applied to the driver are the inputs from the driving simulator. </p><p class="p_Normal">&nbsp;</p>
<p class="p_Normal">In order to use these <span style="font-style: italic;">Driver Demands</span> channels as inputs from the driving simulator the <span style="font-weight: bold;">vidrvsim.vdf</span> file must be used in the event specification of the VI-CarRealTime model.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">The usefulness of having these two categories is that the inputs without the prefix &quot;user&quot; can be used to perform other different maneuvers (for example to implement some basic ADAS logics) and switching to them by setting the <span style="font-style: italic;">user_maneuver_ID</span> signal (if 0 driver will maintain its maneuvers switch logic, otherwise the input will represent the maneuver id that will be performed), while the user inputs are used as inputs from the driving simulator.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal"><span style="font-weight: bold;">Initial Values: </span>this button will open the following window to set desired initial values for the simulation. This value is only applied upon startup of the test, and could be modified during the simulation run.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal" style="text-align: center;"><img alt="drvsim_interface_initial_values" width="634" height="369" style="margin:0px auto 0px auto;width:634px;height:369px;border:none" src="drvsim_interface_initial_values.png"/></p>
<p class="p_Normal" style="text-align: center;">&nbsp;</p>
<p class="p_Normal" style="text-align: center;">&nbsp;</p>

<!--ZOOMSTOP-->
</div></div>
<script type="text/javascript"> 
<!-- 
var lastSlashPos = document.URL.lastIndexOf("/") >
document.URL.lastIndexOf("\\") ? document.URL.lastIndexOf("/") :
document.URL.lastIndexOf("\\");
if( document.URL.substring( lastSlashPos + 1, lastSlashPos + 4
).toLowerCase() != "~hh" )
{
    nsrInit();
}
--> 
</script> 
</body>
</html>
